Upgrading from Hewlett-Packard LAN Manager for OS/2 and MS-DOS to Microsoft LAN Manager 2.1 If you are a user of HP LAN Manager for OS/2 and MS-DOS READ ME FIRST !!! November 15, 1991 Table of Contents 1. An Overview of Migrating to Microsoft LAN Manager 2.1 2. Deciding when to upgrade to Microsoft LAN Manager 2.1 3. Steps for Upgrading to Microsoft LAN Manager 2.1 4. HP Support for Microsoft LAN Manager 2.1 5. Concluding Note APPENDIX A: Network Architecture Overview APPENDIX B: Specific Upgrade Information for HP LAN Manager 1.x Customers Supplemental Instructions for Integration of Microsoft LAN Manager 2.1 with HP Systems and Networking Services Dear HP OS/2 LAN Manager Customer, Congratulations on purchasing the upgrade from HP LAN Manager 1.x for OS/2 and MS-DOS to Microsoft LAN Manager 2.1. In January 1991, Hewlett-Packard announced that HP LAN Manager 1.1 would be HP's last release of the product and that future versions of OS/2 LAN Manager would be made available by Microsoft. Hewlett-Packard networking divisions are now concentrating on delivering and supporting future versions of Microsoft LAN Manager on the HP 9000 (LAN Manager/X) and HP 3000 computer systems (LAN Manager/XL Named Pipes and Resource Sharing). This work includes a continued effort in the development and tuning of networking technologies for DOS and OS/2 clients. At HP, we are continuing our support of LAN Manager. We are contributing a great deal of effort to building and maintaining LAN Manager products and our long term plans continue to include LAN Manager. Hewlett-Packard will continue to offer: - HP LAN Manager/X 9000 server - HP Resource Sharing for the HP 3000 - HP LAN Manager/XL Named Pipes for the HP 3000 - HP Networking Services / MS-DOS - HP ARPA Services / MS-DOS TCP/IP: Hewlett-Packard and Microsoft are pleased to announce that Microsoft has incorporated Hewlett-Packard's Transmission Control Protocol / Internet Protocol (TCP/IP) into the Microsoft LAN Manager 2.1 product, providing the first phase of interoperability between PC clients and all HP minicomputers. Purpose of this document: This supplement, together with the Microsoft LAN Manager 2.1 documentation, is designed to help users of HP LAN Manager for OS/2 and MS-DOS (D1809A, D1809B, D1810A and D1810B) easily and successfully upgrade to Microsoft LAN Manager 2.1. Please note that in this document "HP LAN Manager 1.x" is used instead of the complete product name "HP LAN Manager for OS/2 and MS-DOS v 1.0 or 1.1". ================================================================= 1. An Overview of Migrating to Microsoft LAN Manager 2.1 The current HP LAN Manager product family includes the following products: - HP LAN Manager for OS/2 and MS-DOS (D1809B & D1810B) - HP LAN Manager/X 9000 server (B1011B & B1003B) - HP Resource Sharing for the HP 3000 (B1718A & B1727A) - HP LAN Manager/XL Named Pipes for the HP 3000 (32015A) - HP Networking Services 2.1 / MS-DOS (D1811B) - HP ARPA Services 2.1 / MS-DOS (D1812B) Microsoft LAN Manager 2.1 is the replacement for HP LAN Manager 1.x for OS/2 and MS-DOS. HP will continue to maintain and enhance the rest of the LAN Manager family of products. Some HP LAN Manager 1.x users will be able to upgrade to Microsoft LAN Manager 2.1 immediately without losing any of their current capability. Other HP LAN Manager 1.x users will want to obtain upgraded versions of other HP PC networking products before upgrading to Microsoft LAN Manager 2.1. The remainder of this section provides an overview of the factors to consider in deciding when to install Microsoft LAN Manager 2.1. Section 2 provides more specific information to help you make that decision. The following shows which products and versions are supported with Microsoft LAN Manager 2.1: - HP LAN Manager/X 9000 server: any version later than 1.1 (available 2nd quarter 1992)(1) - HP Network Services 2.2 / MS-DOS (available 2nd quarter 1992) - HP ARPA Services 2.2 / MS-DOS (available 2nd quarter 1992) - HP Resource Sharing for the HP 3000(2) (However, Resource Sharing users will now be required to purchase HP Network Services 2.2 / MS-DOS to add Resource Sharing connectivity to the Microsoft LAN Manager 2.1 DOS client) - HP LAN Manager/XL Named Pipes for the HP 30002 If you are in either of the following situations, then you will want to install Microsoft LAN Manager 2.1 immediately: - you are using HP LAN Manager 1.x in a standalone environment, without any other HP PC network products. - you have HP 9000 or HP 3000 mini-computers on your network, but the clients have no need to access them over the network. If you are using HP LAN Manager 1.x with other HP PC networking products (HP LAN Manager/X, HP LAN Manager/XL Named Pipes, HP Resource Sharing, HP Network Services, or HP ARPA Services) then you may need to obtain upgraded versions of those HP PC networking products before upgrading to Microsoft LAN Manager 2.1. See section 2 for details. 2. Deciding when to upgrade to Microsoft LAN Manager 2.1 The following tables describe different configurations of HP LAN Manager 1.x and what is needed to complete the upgrade to Microsoft LAN Manager 2.1. If you are using multiple features described in the left-hand column, then you should do all the action steps described in the middle column. If you have HP LAN Manager Clients running MS-DOS/Windows: Note: HP LAN Manager 1.x clients are shipped with both HP LAN Manager 1.x and HP 9000 LAN Manager/X. ================================================================= DOS LAN Manager client is using: Action Notes File and print sharing to: * HP LAN Manager 1.x server * Microsoft 2.1 server * HP 3000 LAN Manager/XL Named Pipes Upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 9000 LAN Manager/X server Upgrade the HP 9000 LAN Manager/X server(3) to any version after 1.1 and then upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 3000 Resource Sharing Purchase HP NS 2.2 or later in addition to Microsoft LAN Manager 2.1 to maintain connectivity to Resource Sharing Microsoft LAN Manager 2.1 plus NS 2.2 can also connect to OfficeShare servers, but this is not supported Terminal emulation and file transfer using HP NS services 2.x Upgrade to HP NS 2.2 or later to work correctly with Microsoft LAN Manager 2.1 Terminal emulation and file transfer using HP ARPA services 2.x Upgrade to HP ARPA 2.2 or later to work correctly with Microsoft LAN Manager 2.1 Example: If you are using an HP DOS LAN Manager 1.x client to do file and print sharing to an HP LAN Manager 1.x server and are also doing terminal emulation using HP Network Services, then, to upgrade to Microsoft LAN Manager 2.1, you need to: 1. obtain HP Network Services 2.2 or later 2. upgrade the client to Microsoft LAN Manager 2.1 3. install HP Network Services 2.2 If you have HP LAN Manager Clients running OS/2: Note: HP LAN Manager 1.x clients are shipped with both HP LAN Manager 1.x and HP 9000 LAN Manager/X. ================================================================= OS/2 LAN Manager client is using: Action Notes File and print sharing to: * HP LAN Manager 1.x server * Microsoft 2.1 server Upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 9000 LAN Manager/X server Upgrade the HP 9000 LAN Manager/X servers to any version after 1.1 and then upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 3000 Resource Sharing * OfficeShare servers HP does not provide a solution for OS/2 clients to connect to Resource Sharing or OfficeShare servers at this time If you have OfficeShare clients: ================================================================= OfficeShare client is using: Action Notes File and print sharing to: * HP LAN Manager 1.x server Upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 9000 LAN Manager/X server Upgrade the HP 9000 LAN Manager/X server to any version after 1.1 and then upgrade to the Microsoft LAN Manager 2.1 client File and print sharing to: * HP 3000 Resource Sharing Purchase HP NS 2.2 or later in addition to Microsoft LAN Manager 2.1 to maintain connectivity to Resource Sharing Microsoft LAN Manager 2.1 plus NS 2.2 can also connect to OfficeShare servers, but this is not supported Terminal emulation and file transfer to an HP 3000 Upgrade to HP NS 2.2 or later to work correctly with Microsoft LAN Manager 2.1 Terminal emulation and file transfer to an HP 9000 Upgrade to HP ARPA 2.2 or later to work correctly with Microsoft LAN Manager 2.1 If you have HP LAN Manager 1.x servers: ================================================================= HP LAN Manager OS/2 server with the following clients connected to it: Action Notes * HP LAN Manager 1.1 clients * Microsoft LAN Manager 2.1 clients Upgrade to the Microsoft LAN Manager 2.1 server You can also upgrade the server when using HP LM 1.0 clients (TCP/IP) with connectivity to HP LM/X enabled * HP OfficeShare clients Upgrade the OfficeShare clients to Microsoft LAN Manager 2.1 and then the server to Microsoft LAN Manager 2.1 If you are using HP LM 1.0 clients (TCP/IP) with connectivity to HP LM/X disabled you must upgrade the client to Microsoft LAN Manager 2.1 and then upgrade the server ================================================================= 3. Steps for Upgrading to Microsoft LAN Manager 2.1 3.1 Overview Upgrade steps: 1. Backup one client. Upgrade that client (see section 3.2) and verify that it still works with your current server. 2. Backup one server. Upgrade that server (see section 3.3) to OS/2 1.3 and Microsoft LAN Manager 2.1 and verify that it still works with an HP LAN Manager 1.x client and also with the new Microsoft LAN Manager 2.1 client. Test critical applications. 3. Make any further changes to complete the server configuration. Re-test clients. 4. Upgrade other clients on your network(s). 5. Upgrade other servers on your network(s). 3.2 Upgrading Clients 3.2.1 How do I upgrade a client? 1. Verify MS-DOS 3.3 (or later) or OS/2 1.3. [Note: see Appendix B, Section 3] 2. Run HP LAN Manager 1.x NETSETUP: a. View Configuration. b. Write down all parameters. c. Return to Main screen. d. Remove networking. 3. Reboot. 4. Put Microsoft LAN Manager 2.1 installation disk in Drive A:. 5. Run Microsoft LAN Manager 2.1 SETUP: a. Choose install. b. Re-enter parameters recorded in step 2b above. [Note: For HP network interface cards, see Appendix B, Section 1] [Note: For protocol selection, see Appendix B, Section 4] c. Set Domain to LANGROUP (for further information on Domains, see Appendix B, Section 5) 6. If your network interface card is not set to factory-default values, see Appendix B, Section 2. 3.3 Upgrading Servers 3.3.1 How do I upgrade a server? 1. Backup the server. 2. Run HP LAN Manager 1.x NETSETUP: a. View Configuration. b. Write down all parameters. 3. Save selected files (see Appendix A of the Microsoft LAN Manager 2.1 "Installation and Configuration Guide"). 4. Upgrade to OS/2 version 1.3 and the high performance file system (see Appendix A of the Microsoft LAN Manager 2.1 "Installation and Configuration Guide"). If you are using an HP Vectra see Appendix B, Section 3. 5. Put Microsoft LAN Manager 2.1 installation disk inDrive A:. 6. Run Microsoft LAN Manager 2.1 SETUP: a. Choose install. b. Re-enter parameters recorded in step 2b above. [Note: For HP network interface cards, see Appendix B, Section 1] [Note: For protocol selection, see Appendix B, Section 4] c. Set Domain to LANGROUP (for further information on Domains, see Appendix B, Section 5). 7. Restore files (see Appendix A of the Microsoft LAN Manager 2.1 "Installation and Configuration Guide"). 8. Convert accounts database to Microsoft LAN Manager 2.1 format (see Appendix A of the Microsoft LAN Manager 2.1 "Installation and Configuration Guide"). 9. If your network interface card is not set to factory-default values, see Appendix B, Section 2. 10. If your network will contain a mixture of HP LAN Manager 1.x and Microsoft LAN Manager 2.1 servers and clients, see Appendix B, Section 6. ================================================================= 4. HP Support for Microsoft LAN Manager 2.1 HP LAN Manager 1.x customers who choose to upgrade to Microsoft LAN Manager 2.1 can continue to receive support for LAN Manager from HP. Microsoft and Hewlett-Packard have signed an agreement which authorizes HP to support Microsoft LAN Manager 2.1 and subsequent versions. Microsoft LAN Manager will be supported under the HP PC- LAN Support Service. For more information on the HP PC-LAN Support Service or to purchase the appropriate support for Microsoft LAN Manager 2.1, contact your local HP Sales Representative. ================================================================= 5. Concluding Note Congratulations on the successful installation of Microsoft LAN Manager 2.1. Hewlett-Packard invites you to look at other HP products for your LAN Manager clients, including HP Network Services/MS-DOS (version 2.2) and HP ARPA Services/MS-DOS (version 2.2) and HP server products including HP LAN Manager/X, HP Resource Sharing for the HP 3000 and HP LAN Manager/XL Named Pipes for the HP 3000. For more information on these and other products from HP, contact your HP Sales Representative or HP Dealer. ================================================================= APPENDIX A: Network Architecture Overview HP OfficeShare architecture The HP OfficeShare network operating system is based on the MS-NET network operating system for DOS servers and DOS clients. HP OfficeShare depends on the DOS redirector for file and print services. The redirector makes network devices (such as files and printers at a server) appear as if they were local devices on the local computer. HP OfficeShare's MS-NET architecture has been replaced by HP LAN Manager 1.x and Microsoft LAN Manager 2.1. HP OfficeShare clients will not be able to connect to Microsoft LAN Manager 2.1 servers. Microsoft LAN Manager 2.1 clients will be not be able to connect to HP OfficeShare servers. Current HP OfficeShare customers should upgrade to Microsoft's LAN Manager 2.1. HP LAN Manager 1.x architecture HP LAN Manager 1.x is HP's network operating system for OS/ servers, OS/2 clients and DOS clients and is a combination of HP, 3Com and Microsoft technologies. HP LAN Manager 1.x does not support versions of OS/2 higher than 1.1 on servers or OS/2 clients. If you want to run higher versions of OS/2, you must use the LAN Manager 2.1 product from Microsoft. HP LAN Manager 1.x uses the Network Driver Interface Specification (NDIS) architecture to support a variety of network protocols and interface cards. HP LAN Manager 1.x also uses the Demand Protocol Architecture (DPA) to allow DOS clients to load and unload multiple protocol stacks to/from memory. HP LAN Manager 1.x also provided the capability for OS/2 clients to connect to HP 3000 Resource Sharing and HP OfficeShare servers. This capability is not provided by Microsoft LAN Manager 2.1, and HP is not planning to provide this capability for OS/2 clients either. Users who require this capability for OS/2 clients should stay with their existing version of HP LAN Manager 1.x. Although it is possible to maintain a "mix" of HP LAN Manager 1.x and Microsoft LAN Manager 2.1 clients on a network, HP recommends that customers convert all DOS and OS/2 clients to Microsoft LAN Manager 2.1 (subject to the temporary ARPA, NS and LAN Manager/X limitations noted earlier in this paper). By upgrading to Microsoft LAN Manager 2.1, HP LAN Manager 1.x customers can get the enhancements they need without losing the core functionality of HP LAN Manager 1.x. Microsoft LAN Manager 2.1 architecture Microsoft LAN Manager 2.1 is Microsoft's newest network operating system for OS/2 servers, and OS/2 and DOS clients. In Microsoft LAN Manager 2.1 systems, Microsoft has enhanced domain administration and other features of the architecture used in HP LAN Manager 1.x. Microsoft LAN Manager 2.1 servers and OS/2 clients require OS/2 version 1.21 (or later). A special server version of OS/2 1.3 is included with the Microsoft LAN Manager 2.1 product. Like HP LAN Manager 1.x, Microsoft LAN Manager 2.1 uses the NDIS architecture and is protocol independent. Microsoft LAN Manager 2.1 has significant enhancements over the HP LAN Manager 1.x implementation. By upgrading to Microsoft LAN Manager 2.1, you'll get the following benefits of the Microsoft LAN Manager 2.1 architecture: Improved speed. The High Performance File System (HPFS 386) is a fast 32-bit kernel-level file I/O system that provides improved performance. Enhanced security. Each network resource can be controlled (directories, subdirectories, individual files, print queues and peripherals). User access rights are checked transparently after the user's initial logon. As an administrator, you can control valid logon times, valid clients, account expiration dates, password length and password aging for each user. For extra security, passwords are DES-encrypted. A secure shell and local security can protect resources against unauthorized access. Network auditing tracks the use of network resources. Advanced multi-server administration tools. Domains enable you to administer multiple resources for multiple users in one step. Groups let you set privileges across multiple resources for multiple users in one step. A primary domain controller updates user accounts at backup and member servers on the domain. The replicator service can automatically replicate changes to specified files to designated servers or OS/2 clients. Multiple concurrent NetBIOS protocol support on OS/2 and DOS Enhanced nodes. DOS Enhanced and OS/2 clients can use multiple NetBIOS protocols concurrently, while DOS Basic clients can use different NetBIOS protocols (one at a time). Improved Demand Protocol Architecture functionality. (For Microsoft LAN Manager 2.1 and later releases, DPA refers to the ability of DOS clients to load/unload an entire protocol stack, rather than the ability to load/unload individual TCP/IP modules as in HP LAN Manager 1.x.) Fault tolerance. These features are available: uninterruptible power supply (UPS) support, disk mirroring (this pairs a hard drive with a duplicate backup for data protection if one drive fails), and disk duplexing (this is the same as disk mirroring except that the two hard disks are controlled by separate disk controllers). NetWare connectivity. This feature allows LAN Manager clients to access NetWare servers. Peer services. OS/2 clients can function as limited servers and can be used to share printers or files. Client-server application platform. Named pipes and mailslots. Home directories. In Microsoft LAN Manager 2.1, an administrator can set up a home directory for each user. Users can directly access their home directory shares (without having to know the server and share name by typing net use H: /home (where H: is an unassigned drive name). ================================================================= APPENDIX B: Specific Upgrade Information for HP LAN Manager 1.x Customers 1. Network Interface Card selection Some of the HP network interface cards supported by HP LAN Manager 1.x will not explicitly show up in the documentation and SETUP program for Microsoft LAN Manager 2.1. These additional HP network interface cards are still supported for Microsoft LAN Manager 2.1. If you are using one of the following HP network interface cards, choose "HP Ethertwist Adapter (All Cards)" in SETUP. Network Interface Card Select in SETUP utility - HP EtherTwist Adapter Cards- 27245A,27247A,272 67A HP Ethertwist Adapter (All Cards) - HP EtherTwist MicroChannel Adapter Card - 27246A " - HP StarLAN 10 PC Card II 27240A " - HP StarLAN 10 MicroChannel Card 27241A " - HP ThinLAN Adapter Card 27250A " (All of the above HP network interface cards use the HPLAN.DOS or HPLAN.OS2 driver.) The following additional HP network interface cards are supported (for clients ONLY), but are not listed in the Microsoft LAN Manager 2.1 documentation or listed in SETUP. If you are using one of the following HP network interface cards, choose "3Com Etherlink Adapter" in SETUP. Network Interface Card Select in SETUP utility - HP StarLAN 10 Vectra PC Adapter Card 27236A 3Com EtherLink Adapter - HP ThinLAN/Vectra PC Adapter Card 27210A/27210B " (All of the above HP network interface cards use the ELNK.DOS or ELNK.OS2 driver.) If you are not using one of these network interface cards, then follow the Microsoft LAN Manager 2.1 directions as given. 2. Network Interface Card Configuration The HP LAN Manager 1.x configuration utility (NETSETUP) allows users to configure network interface card parameters inside NETSETUP. These parameters are things like Interrupt Channel, I/O address, etc. The current card parameters and network names, addresses, etc. can be obtained by running the HP LAN Manager NETSETUP program. You should view and record these parameter values before running the Microsoft LAN Manager 2.1 configuration utility (SETUP) The LAN Manager SETUP program does not ask for network interface card parameters and sets the values to the factory default values for the card. If your network interface card is not set to the factory default values, you must edit the PROTOCOL.INI file yourself. The Microsoft "LAN Manager Installation and Configuration Guide" has more detailed information on this topic. If you see a "failed to bind" or "can't find server" error message when attempting to load LAN Manager, it may mean that you have not properly set the network interface card parameters in PROTOCOL.INI. 3. MS-DOS and OS/2 Versions Supported Microsoft LAN Manager 2.1 DOS clients must use MS-DOS version 3.3 or later (version 5.0 is recommended). HP LAN Manager 1.x clients using a version earlier than MS-DOS 3.3 must upgrade. Microsoft LAN Manager 2.1 OS/2 servers and OS/2 clients must use Microsoft's 1.21 (or later) version of OS/2 (version 1.3 is strongly recommended). Microsoft's OS/2 versions 1.21 and 1.3 have been tested and are supported on all HP Vectra 80386 and 80486-based personal computers. OS/2 version 1.3 is not supported for 8088 or 80286-based personal computers, such as HP Vectra ES, CS, LS or A/A+ models. [The only HP 80286-based personal computer that supports OS/2 1.3 is the 286/12 and it is not supported for use as a Microsoft LAN Manager 2.1 server.] 4. Protocol Selection HP LAN Manager 1.0 customers who are using the NBP protocol may want to convert to Microsoft LAN Manager 2.1 with NetBEUI protocol. NetBEUI offers small memory consumption and excellent performance features, plus the advantage of future support and enhancement from Microsoft. NetBEUI also supports source routing on IBM token ring networks and is the standard protocol in most OEM implementations of LAN Manager. The Microsoft "LAN Manager Installation and Configuration Guide" has more detailed information on this topic. HP LAN Manager 1.0 customers who are using the XNS, DLC or NBP protocols and who want to continue to use these protocols should refer to the "Microsoft Upgrade Toolkit for 3Com Networks" for detailed information on how to accomplish this. Most HP LAN Manager 1.x customers will want to continue to use the TCP/IP protocol and will choose "TCP/IP" instead of "NetBEUI" in Microsoft LAN Manager 2.1 SETUP. TCP/IP offers small memory consumption, excellent performance and the ability to connect DOS clients to HP LM/X, HP 3000 Resource Sharing and HP 3000 LAN Manager/XL Named Pipes servers. 5. Domain Name In Microsoft LAN Manager 2.1, the group of workstations and servers to which it belongs is called a domain. For Microsoft LAN Manager 2.1 nodes, the domain name is specified in the DOMAIN=domainname line of the LANMAN.INI file. For HP LAN Manager 1.x nodes, the domain name is specified in the LANGROUP=domainname line of the LANMAN.INI file. Being on a different domain does not prevent a workstation from accessing resources on a server on another domain; however, the domain is important when using the net logon and net view commands. The net view command only lists the servers that have specified the same domain name and the same protocol as the workstation issuing the net view. The domain also determines which servers can send domain-based messages to the workstation. The result is that by default, HP LAN Manager 1.x workstations only see HP LAN Manager 1.x servers when a net view command is performed. Similarly, only Microsoft LAN Manager 2.1 servers in the default group "DOMAIN" are visible when a net view command is performed from a standard Microsoft LAN Manager 2.1 client. A client can still use resources on a server that doesn't appear in the net view list, assuming that a valid user name and password for that server are used on the client and that both nodes are using the same protocol. A user can also explicitly view any LAN Manager server on the local network, regardless of grouping, by typing: net view \\servername By default, the net logon command sends a logon request the domain specified in the DOMAIN line (in Microsoft LAN Manager 2.1) or LANGROUP line (in HP LAN Manager 1.x) of LANMAN.INI so that the user can log on to the network with the specified domain. However, the user can use the /domain:domainname option with the net logon command to specify a domain other than the domain set in the LANMAN.INI file. If you put both an HP LAN Manager 1.x and a Microsoft LAN Manager 2.1 network on the same domain, a user can log on to both networks with a single net logon command--if user has the same account name and password on the Microsoft LAN Manager 2.1 domain controller's user accounts database and on HP LAN Manager 1.x server user accounts databases. The key point is that you should put both servers on the same domain; otherwise, one network won't be able to view all servers on both networks at once and logging on to both networks is unnecessarily cumbersome. To place both networks on the same domain, you will need to change the domain name for all nodes to match the selected domain name. For example: At each HP LAN Manager 1.x client and server, modify the LANMAN.INI file by setting the LANGROUP parameter to match the DOMAIN parameter of each Microsoft LAN Manager 2.1 client and server. Alternatively, at each Microsoft LAN Manager 2.1 client and server, you could modify the LANMAN.INI file by setting the DOMAIN parameter to LANGROUP parameter at HP LAN Manager 1.x nodes. Either of these solutions will work for all LAN Manager clients and servers of both types. There is another simpler approach that ensures that Microsoft LAN Manager 2.1 clients will be able to see both types of servers, but this solution will not work on HP LAN Manager 1.x clients. If this is appropriate for your situation, modify the LANMAN.INI file, giving the OTHDOMAINS parameter a value that matches the LANGROUP parameter of the HP LAN Manager 1.x network. (SETUP also gives you the option of doing this during Microsoft LAN Manager 2.1 client installation.) Once the parameter is set and the client is restarted, the Microsoft LAN Manager 2.1 client can see servers in both the "LANGROUP" group and the "DOMAIN" group when using net view. Unfortunately, the OTHDOMAINS parameter is not supported with HP LAN Manager 1.x. For further information on the net view and net logon commands or the LANGROUP, DOMAIN and OTHDOMAINS parameters, see the HP LAN Manager 1.x or Microsoft LAN Manager 2.1 documentation. 6. Managing Security Just as with HP LAN Manager 1.x, Microsoft LAN Manager 2.1 OS/2 networks have share-level, user-level and logon security available. To access each type of network, a user must have an account in the desired network's user accounts database. The user can use the specific logon command for the desired network to request access to that network. Although the logon commands are the same (net logon), the Microsoft LAN Manager 2.1 and HP LAN Manager 1.x Netlogon services are distinct services. On mixed HP LAN Manager 1.x and Microsoft LAN Manager 2.1 networks, a Microsoft LAN Manager 2.1 server running the Netlogon service handles the user's logon request and validates the user if an account exists and the correct password is specified. Microsoft LAN Manager 2.1 networks have distributed user accounts databases. This means that every Microsoft LAN Manager 2.1 server that participates in the Netlogon service on a single domain has an updated copy of the master user accounts database at the primary domain controller. A Microsoft LAN Manager 2.1 primary domain controller (or backup domain controller) uses the master user accounts database (or an updated copy of it) to validate user logon requests. On the other hand, HP LAN Manager 1.x networks have separate, independent user accounts databases at each HP LAN Manager 1.x server. HP LAN Manager 1.x user accounts databases are not synchronized; therefore, each server must be updated individually. On a mixed HP LAN Manager and Microsoft LAN Manager 2.1 network, HP LAN Manager 1.x servers have the same role as Microsoft LAN Manager 2.1 standalone servers. HP LAN Manager 1.x servers can have user-level security, but they do not participate in a domain-wide Netlogon service. When a user logs on with the net logon command on to a mixed HP LAN Manager 1.x and Microsoft LAN Manager 2.1 network, that user is validated by a Microsoft LAN Manager 2.1 domain controller (primary or backup). The net logon command registers the user's user name and password in the redirector to be used as the default user name and password enabling user access to HP LAN Manager 1.x servers. Because HP LAN Manager 1.x servers and Microsoft LAN Manager 2.1 standalone servers must be updated individually and are not necessarily synchronized with the Microsoft LAN Manager 2.1 master database, a validated user has access to those servers only if the user has an up-to-date account (an account that matches the default user name and password) on those servers. In the HP LAN Manager 1.x client configuration, you specify either (1) the server you want to validate your logon; or (2) an '*' to allow any server to do so. If #1 is selected, only that server can validate the user. If that server is unable to validate, the user will not get on. If #2 is selected, it is possible that an HP LAN Manager 1.x server may validate the user; i.e. the HP LAN Manager 1.x server may be faster than the Microsoft LAN Manager 2.1 domain controller in validating the user. - Microsoft and MS-DOS are registered trademarks of Microsoft Corporation - Windows is a trademark of Microsoft Corporation - HP LAN Manager/X is based on Microsoft LAN Manager for UNIX Systems - HP LAN Manager is based on Microsoft LAN Manager and on 3+Open - 3+Open is a trademark of 3Com Corporation - 3Com is a registered trademark of 3Com Corporation in the U.S. and other countries. - OS/2 is a U.S. Registered Trademark of Microsoft Corporation and International Business Machines Corporation 1 - HP LAN Manager clients provided with HP LAN Manager/X work with Microsoft LAN Manager 2.1 servers. See Section 2 for details. 2 - Based on the best information available at the time of publication these products do not need to be upgraded for Microsoft LAN Manager 2.1 clients. A new version of these products might be necessary in the future to support Microsoft LAN Manager 2.1 clients. Contact your HP Sales Representative or Dealer for the most current information. 3 - The only problem with HP LAN Manager/X 1.1 that HP is currently aware of is that when you do printing inside Windows applications that are connected to HP LAN Manager/X printers, a error dialog box comes up with Network Error. Selecting retry allows the printout to complete.